Trunk management in simulated Fibre channel trunking system environment

ABSTRACT

In a Fibre channel (FC) networking system, a first FC networking device includes a first Ethernet switch processor and a first FC PHY converter that is communicatively coupled to the first Ethernet switch processor via a first plurality of Ethernet links, where the first plurality of Ethernet links is grouped as a first Ethernet aggregation interface. A second FC networking device is communicatively coupled to the first FC networking device via a plurality of FC links, where each Ethernet link of the first plurality of Ethernet links is mapped to a corresponding FC link of the plurality of FC links. The first FC networking device is configured to: generate only one FLOGI for a FC trunk associated with the first Ethernet aggregation interface; and hash the FLOGI among the first plurality of Ethernet links so as to the second FC networking device via the first Ethernet aggregation interface.

CROSS-REFERENCE TO PRIOR APPLICATIONS

This patent application is a continuation-in-part application to and claims priority benefit under 35 USC § 120 to co-pending and commonly-owned U.S. patent application Ser. No. 16/144,037, filed on Sep. 27, 2018, entitled “Simulated Fibre Channel Trunking System”, which patent document is incorporated by reference herein in its entirety and for all purposes.

BACKGROUND

The present disclosure relates generally to information handling systems, and more particularly to systems and methods for simulating Fibre Channel (FC) trunking using Ethernet links.

As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.

Some information handling systems provide a Fibre Channel (FC) Storage Area Network (SAN) for the storage of data. In such systems, an FC switch may be utilized to couple the FC SAN to servers via a Fibre Channel Forwarder (FCF) that performs FC over Ethernet (FCoE)-to-FC protocol conversions on Ethernet communications sent from the servers to the FC SAN, as well as FC-to-FCoE protocol conversions on FC communications sent from the FC SAN to the servers. Such FCFs allow servers that communicate via the Ethernet protocol to utilize FC SANs that communicate via the FC protocol. In addition, the FCFs may allow servers to communicate via the FC protocol as well. However, the conventional functionality of such FCFs raises a number of issues.

For example, servers in such systems may utilize a Converged Network Adapter (CNA) to communicate with an N_Port ID Virtualization (NPIV) Proxy Gateway (NPG) in the FCF in order to provide login communication for logging into the FC SAN, with the FCF converting those login communications, and the NPG providing the converted login communications to the FC switch in order to log the server into the FC SAN. The NPG may establish links with the FC switch via, for example, a plurality of virtual uplinks with servers on each physical link provided between the NPG and the FC switch, and may operate to load balance logins received from servers via those links. As such, each of the physical FC links between the NPG and the FC switch may be trunked or otherwise grouped together as a single interface such that traffic between the NPG and the FC switch can be load balanced between the physical FC links. However, in conventional FC SANs, trunking the FC links between the NPG and the FC switch require FC level handshaking operations such as logging in the various N_Ports on the NPG with the F_Ports on the FC switch. This requires an expensive and proprietary FC switch chip.

Accordingly, it would be desirable to provide an improved Fibre Channel trunking system.

BRIEF DESCRIPTION OF THE DRAWINGS

References will be made to embodiments of the disclosure, examples of which may be illustrated in the accompanying figures. These figures are intended to be illustrative, not limiting. Although the accompanying disclosure is generally described in the context of these embodiments, it should be understood that it is not intended to limit the scope of the disclosure to these particular embodiments. Items in the figures may be not to scale.

FIG. 1 is a schematic view illustrating an embodiment of an information handling system.

FIG. 2 is a schematic view illustrating an embodiment of a simulated Fibre Channel (FC) trunking system.

FIG. 3 is a schematic view illustrating an embodiment of a server device in the simulated FC trunking system of FIG. 2.

FIG. 4 is a schematic view illustrating an embodiment of an FC networking device in the simulated FC trunking system of FIG. 2.

FIG. 5 is a flow chart illustrating an embodiment of a method for simulating FC trunking using Ethernet links.

FIG. 6 is a schematic view illustrating an embodiment of the simulated FC trunking system of FIG. 2 during the method of FIG. 5.

FIG. 7 is a flow chart illustrating an embodiment of a method for processing a login on the simulated FC trunking system of FIG. 6.

FIG. 8 is a schematic view illustrating an embodiment of a simulated FC trunking system that has an added trunk member.

FIG. 9 is a flow chart illustrating an embodiment of a method for adding a trunk member to a simulated FC trunking system.

FIG. 10 is a flow chart illustrating an embodiment of a method for deleting a trunk member from a simulated FC trunking system.

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, calculate, determine, classify, process, transmit, receive, retrieve, originate, switch, store, display, communicate, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer (e.g., desktop or laptop), tablet computer, mobile device (e.g., personal digital assistant (PDA) or smart phone), server (e.g., blade server or rack server), a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, touchscreen and/or a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components.

In one embodiment, IHS 100, FIG. 1, includes a processor 102, which is connected to a bus 104. Bus 104 serves as a connection between processor 102 and other components of IHS 100. An input device 106 is coupled to processor 102 to provide input to processor 102. Examples of input devices may include keyboards, touchscreens, pointing devices such as mouses, trackballs, and trackpads, and/or a variety of other input devices known in the art. Programs and data are stored on a mass storage device 108, which is coupled to processor 102. Examples of mass storage devices may include hard discs, optical disks, magneto-optical discs, solid-state storage devices, and/or a variety other mass storage devices known in the art. IHS 100 further includes a display 110, which is coupled to processor 102 by a video controller 112. A system memory 114 is coupled to processor 102 to provide the processor with fast storage to facilitate execution of computer programs by processor 102. Examples of system memory may include random access memory (RAM) devices such as dynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memory devices, and/or a variety of other memory devices known in the art. In an embodiment, a chassis 116 houses some or all of the components of IHS 100. It should be understood that other buses and intermediate circuits can be deployed between the components described above and processor 102 to facilitate interconnection between the components and the processor 102.

Referring now to FIG. 2, an embodiment of a simulated Fibre Channel (FC) trunking system 200 is illustrated. In the illustrated embodiment, the simulated FC trunking system 200 includes a server device 202 that may be the IHS 100 discussed above with reference to FIG. 1 and/or that may include some or all of the components of the IHS 100. For example, the server device 202 may be one or more servers in a server rack or server chassis, and one of skill in the art in possession of the present disclosure will recognize that any number of servers may be provided in the simulated FC trunking system 200 and may operate similarly to the server devices discussed below. In the illustrated embodiment, the server device 202 is coupled to a Fibre Channel Forwarder (FCF) device 204 that may be the IHS 100 discussed above with reference to FIG. 1 and/or that may include some or all of the components of the IHS 100. For example, the FCF device 204 may be provided by a switch or other networking device that is configured to receive Ethernet communications from the server device 202, convert those Ethernet communications to Fibre Chanel (FC) communications for forwarding to an FC Storage Area Network (SAN), receive FC communications from the FC SAN, convert those FC communications to Ethernet communications for forwarding to the server device 202, and/or perform other FCF device functionality that would be apparent to one of skill in the art in possession of the present disclosure. In another example, the FCF device 204 may be configured to receive FC communications from the server device 202 and forward those FC communications to an FC SAN. In such an example, and as discussed below, the FCF device 204 may include an Ethernet switch processor that is configured to perform the switching functionality for FC communications by converting those FC communications received from the server device 202 to FCoE communications, processing the FCoE communications using an Ethernet switch processor rather than a FC switch processor, converting the processed FCoE communication back to FC communications, and forwarding those FC communications to the FC SAN.

In the illustrated embodiment, the FCF device 204 is coupled via a plurality of FC links (e.g., an FC link 205 a and an FC link 205 b) to an FC switch 206 that may be the IHS 100 discussed above with reference to FIG. 1 and/or that may include some or all of the components of the IHS 100. For example, the FC switch 206 may be provided by a switch that is configured to receive FC communications (e.g., initialized by the server device 202) from the FCF device 204, log the server device 202 into an FC SAN, subsequently receive FC communications (e.g., initialized by the server device 202) from the FCF device 204 to allow the server device 202 to communicate with the FC SAN, and perform a variety of other FC switch functionality that would be apparent to one of skill in the art in possession of the present disclosure. In the illustrated embodiment, the FC switch 206 is coupled to an FC storage system 208 that may be the IHS 100 discussed above with reference to FIG. 1 and/or that may include some or all of the components of the IHS 100. For example, the FC storage system 208 may be provided by a FC SAN that is configured to receive FC communications from the server device 202 through the FC switch 206, send FC communications to the server device 202 through the FC switch 206, and/or perform a variety of other FC storage system functionality that would be apparent to one of skill in the art in possession of the present disclosure.

In the illustrated embodiment, the server device 202 includes an initiator communication system 202 a that may include a Host Bus Adapter (HBA) for FC communications, a Network Interface Controller (NIC) that provides Fibre Channel over Ethernet (FCoE) communications, a Converged Network Adapter (CNA) that includes both an HBA and a NIC, and/or any other communication system that is configured to provide FCoE communications and/or FC communication. The initiator communication system 202 a may be coupled to the FCF device 204 using a cable (e.g., an optical cable, a copper wire cable, and/or other cabling) and/or other coupling system that would be apparent to one of skill in the art in possession of the present disclosure. In an embodiment, the FC storage system 208 includes a target communication system 208 a (e.g., an HBA) that is coupled to the FC switch 206 using a cable or other coupling system known in the art. One of skill in the art in possession of the present disclosure will recognize that the use of “initiator” and “target” with reference to the communication systems 202 a and 208 a is provided for clarity of discussion with regard to the example of server/storage communications discussed below, and different communication scenarios will fall within the scope of the present disclosure as well.

As discussed below, each of the server device 202 and the FC storage system 208 may include memory systems that include instructions that, when executed by processing systems in the server device 202 or FC storage system 208, cause the processing systems to communicate using FC protocols and, in some instances, partially with FCoE protocols, in order to, for example, transport Small Computer System Interface (SCSI) commands over a FC network (e.g., the FC fabric including the FCF device 204 and FC switch 206) provided between them. While a specific simulated FC trunking system 200 is illustrated and described below, one of skill in the art in possession of the present disclosure will recognize that the teachings of the present disclosure will be beneficial for a variety of FC systems that would be apparent to one of skill in the art in possession of the present disclosure and, as such, a wide variety of modifications to the number, types, and orientation of devices in the simulated FC trunking system 200 will fall within the scope of the present disclosure as well.

Referring now to FIG. 3, an embodiment of a server device 300 is illustrated that may be the server device discussed above with reference to FIG. 2. As such, the server device 300 may be the IHS 100 discussed above with reference to FIG. 1 and/or may include some or all of the components of the IHS 100, and in specific examples may be one or more servers in a server rack or server chassis. In the illustrated embodiment, the server device 300 includes a chassis 302 that houses the components of the server device 300, only some of which are illustrated in FIG. 3. For example, the chassis 302 may house a processing system (not illustrated, but which may include the processor 102 discussed above with reference to FIG. 1) and a memory system (not illustrated, but which may include the system memory 114 discussed above with reference to FIG. 1) that includes instructions that, when executed by the processing system, cause the processing system to provide an adapter engine 304 that is configured to perform the functions of the adapter engines and server devices discussed below.

The chassis 302 may also house a storage system (not illustrated, but which may include the storage device 108 discussed above with reference to FIG. 1) that is coupled to the adapter engine 304 (e.g., via a coupling between the storage system and the processing system) and that may include a storage subsystem 306 that is configured to store the data utilized as discussed below. However, in some embodiments the storage subsystem 306 may be omitted. The chassis 302 may also house a communication subsystem 308 that may be the initiator communication system 202 a discussed above with reference to FIG. 2, that is coupled to the adapter engine 304 (e.g., via a coupling between the communication subsystem 308 and the processing system), and that may include a Network Interface Controller (NIC), a wireless communication devices, one or more ports (e.g., a port 308 a), and/or other communication components that would be apparent to one of skill in the art in possession of the present disclosure. Furthermore, in some embodiments, components of the adapter engine 304 and/or the communication subsystem 308 may be provided by a Converged Network Adapter (CNA) that performs the functionality of the adapter engines and/or server devices discussed below. However, in other embodiments, the adapter engine 304 and/or communication subsystem 308 may be utilized to provide other types of adapters (e.g., Host Bus Adapters (HBAs)) while remaining within the scope of the present disclosure as well. While a specific server device 300 has been described, one of skill in the art in possession of the present disclosure will recognize that the server device 300 may include a variety of other components that perform conventional server device functionality, as well as the functionality described below, while remaining within the scope of the present disclosure.

Referring now to FIG. 4, an embodiment of a Fibre Channel (FC) networking device 400 is illustrated that may be the FCF device 204 or the FC switch 206 discussed above with reference to FIG. 2. As such, the FC networking device 400 may be, for example, the IHS 100 discussed above with reference to FIG. 1, and/or which may include some or all of the components of the IHS 100. In the illustrated embodiment, the FC networking device 400 includes a chassis 402 that houses the components of the FC networking device 400, only some of which are illustrated in FIG. 4. For example, the chassis 402 may include a processing system (not illustrated, but which may include the processor 102 discussed above with reference to FIG. 1) and a memory system (not illustrated, but which may include the system memory 114 discussed above with reference to FIG. 1) that includes instructions that, when executed by the processing system, cause the processing system to provide an protocol processing engine 404 that is configured to perform the functions of the protocol processing engines and FC networking devices discussed below.

In another example, the memory system may include instructions that, when executed by the processing system, cause the processing system to provide a grouping engine 405 that is configured to perform the functions of the grouping engines and FC networking devices discussed below. In an embodiment, the processing system that provides the protocol processing engine 404 includes an Ethernet switch processor (e.g., an Ethernet switch chip such as, for example, an Ethernet switch Application Specific Integrated Circuit (ASIC)), and a Central Processing Unit (CPU). In a specific example, the protocol processing engine 404 may be provided by the Ethernet switch processor, and the grouping engine 405 may be provided by the CPU. While in the embodiments discussed below, specific actions are discussed as being performed by the CPU and the Ethernet switch processor, in different embodiments, the actions performed by the CPU may be performed by the Ethernet switch processor and/or some other processing system (e.g., a processing system that performs the actions of both the CPU and the Ethernet switch processor) while remaining within the scope of the present disclosure. In an embodiment, the memory system that includes the instructions for providing the protocol processing engine 404 may include Ethernet layer 2 (L2) forwarding tables. In a specific example, the processing system may execute instructions included on the included on the memory system to provide an N_Port ID Virtualization (NPIV) Proxy Gateway (NPG) engine that operates as discussed below.

In some FC networking devices, FC fabrics utilize FC switch devices that include expensive and proprietary FC switch chips, and the simulated FC trunking system 200 of the present disclosure may provide at least a portion of an FC fabric that includes the FC networking device 400 with an Ethernet switch processor that one of skill in the art will recognize is relatively inexpensive compared to the FC switch chips discussed above due to, for example, the widespread use of Ethernet switch processors in a variety of networking applications and the resulting economies of scale. In the embodiments discussed in further detail below, the FC networking device 400 may provide for the transmission of FC data traffic between server devices and storage devices utilizing an Ethernet switch processor (which operates via a different Open System Interconnect (OSI) physical layer than FC switch chips included in conventional FC switches) along with the converters and software stack discussed below. As discussed above, the processing system that provides the protocol processing engine 404 may also include a Central Processing Unit (CPU) that handles, for example, control protocols and configuration of the FC networking device 400 including, for example, providing the grouping engine 405, while the Ethernet switch processor performs data traffic processing and forwarding.

The FC networking device 400 includes a converter 406 that may include, for example, at least one FC PHY chip and a memory system that includes instructions that, when executed by the at least one FC PHY chip, cause the at least one FC PHY chip to provide an FC-to-FCoE engine 406 a, an FCoE-to-FC engine 406 b, and/or perform any of the other functions of the converter 406 discussed below. As described below, the FC-to-FCoE engine 406 a and/or the FCoE-to-FC engine 406 b may operate as FC/FCoE encapsulator/decapsultors at the physical (PHY) layer, providing an FC port-level state machine, framing, and PHY level FC/FCoE conversion. The FC networking device 400 also includes a converter 408 that may include, for example, an FC PHY chip and a memory system that includes instructions that, when executed by the FC PHY chip, cause the FC PHY chip to provide an FC-to-FCoE engine 408 a, an FCoE-to-FC engine 408 b, and/or perform any of the other functions of the converter 408 discussed below. As described below, the FC-to-FCoE engine 408 a and/or the FCoE-to-FC engine 408 b may operate as FCoE/FC encapsulator/decapsultors at the PHY layer, providing an FC port-level state machine, framing, and PHY level FCoE/FC conversion.

The converter 406 is coupled to a plurality of ports (e.g., a port 410 a, a port 410 b, a port 410 c, and up to a port 410 d) on the FC networking device 400, and the converter 408 is coupled to a plurality of ports (e.g. a port 412 a, a port 412 b, a port 412 c, and up to a port 412 d) on the FC networking device 400. In an embodiment, each of the plurality of ports 410 a-410 d may be coupled to a respective FC PHY chip that is provided in the converter 406, and each of the plurality of ports 412 a-412 d may be coupled to a respective FC PHY chip that is provided in the converter 408. In some embodiments, the ports 410 a-410 d may be ports configured for FC communication and/or ports configured for FCoE communication. The converter 406 may be coupled to the Ethernet switch processor via plurality of links (e.g., a link 414 a, a link 414 b, a link 414 c, and up to a link 414 d), and the converter 408 may be coupled to protocol processing engine 404 via a plurality of links (e.g., a link 416 a, a link 416 b, a link 416 c, and up to a link 416 d). Each link 414 a-414 d and 416 a-416 d may be configured to provide FCoE traffic, and may be referred to herein as an Ethernet link. In an embodiment, each of the plurality of links 414 a-414 d may be coupled to a respective FC PHY chip that is provided in the converter 406, and a respective internal port of the Ethernet switch processor, while each of the plurality of links 416 a-416 d may be coupled to a respective FC PHY chip that is provided in the converter 408, and a respective internal port of the Ethernet switch processor. In embodiments where the ports 410 a, 410 b, 410 c, and/or 410 d are configured for FCoE communication, the converter 406 may be omitted, and the ports 410 a, 410 b, 410 c, and/or 410 d may be coupled directly to the Ethernet switch processor via a respective link 414 a, 414 b, 414 c, and/or 414 d.

Referring now to FIG. 5, an embodiment of a method 500 for simulating Fibre Channel (FC) trunking using Ethernet links is illustrated. As discussed above, a plurality of FC links may be provided between two FC networking devices such as, for example, an FCF and an FC switch. In conventional FC trunking systems, these FC links may be trunked or otherwise grouped together using a link aggregation protocol to form a trunk group that aggregates the FC links such that they are recognized as a single interface. However, trunking the FC links requires FC level handshaking operations such as logging in the various N_Ports of the FCF with the F_Ports of the FC switch. Furthermore, in conventional FC SANs, traffic to and from servers is provided only on the physical FC link used by the server to log in with the FC SAN, which results in uneven traffic balancing or underutilization of available bandwidth on other physical links available between the FCF and the FC switch. The systems and method of the present disclosure remedy these deficiencies by grouping, in FC networking devices that process FC traffic using an Ethernet switch processor (e.g., an Ethernet network processing unit (NPU)), Ethernet links between the Ethernet switch processor and FC PHY chips that provide FC-to-FCoE conversion for ingress traffic and FCoE-to-FC conversion for egress traffic, and presenting the grouped Ethernet links as a single interface. The grouped Ethernet links can simulate an FC trunk group including the FC links between the FCF device and the FC switch because each of the Ethernet links are mapped to a respective FC link between the FCF device and the FC switch. The protocol processing engine may then load balance the FCoE traffic across the grouped Ethernet links using a hashing algorithm, which in turn is converted to FC traffic at the FC PHY chip and provided on its respective FC link. As such, simulated “FC trunking” occurs, and the drawbacks related to FC level handshaking operations associated with forming an FC trunk group using an expensive, proprietary FC switch chip in conventional systems are reduced.

The method 500 begins at block 502 where a plurality of Ethernet links between an Ethernet switch processor and FC PHY converter are grouped together as an aggregated interface. In an embodiment of block 502, and with reference to a simulated FC trunking system 600 of FIG. 6 (which may be provided in an embodiment of the simulated FC trunking system 200 referenced above in FIG. 2), the FCF device 204 may be coupled to the FC switch 206 via FC links 602 a and 602 b (which may be the FC links 205 a and 205 b referenced above in FIG. 2.) For example, the port 412 a of the FCF device 204 may be coupled to the port 410 a of the FC switch 206 via the FC link 602 a, and the port 412 b of the FCF device 204 may be coupled to the port 410 b of the FC switch 206 via the FC link 602 b. In various embodiments, the ports 412 c and 412 d may not be coupled to the FC switch 206, as illustrated in FIG. 6. In the illustrated example, the ports 412 a and 412 b of the FCF device 204 are N_Ports, while the ports 410 a-410 b of the FC switch 206 are F_Ports. In conventional FC trunking systems, the links 602 a and 602 b may be grouped together as a trunk group that is presented as a single interface to the server device 202 and/or the FC storage system 208. For example, the FCF device 204 may group the ports 412 a and 412 b, and the FC switch 206 may group the ports 410 a and 410 b. However, as discussed above, trunking or otherwise aggregating FC links provides a number of drawbacks when compared to aggregating Ethernet links.

As such, in an embodiment of block 502, the grouping engine 405 of the FCF device 204 aggregates the Ethernet links 416 a and 416 b between the converter 408 and the protocol processing engine 404 provided by the Ethernet switch processor. For example, the grouping engine 405 of the FCF device 204 may group the internal ports of the Ethernet switch processor that are mapped to the FC PHYs that are both provided by the converter 408 and coupled to the ports 412 a and 412 b that would otherwise make up a FC trunk group between the FCF device 204 and the FC switch 206. As illustrated, the grouping of the internal ports of the Ethernet switch processor in the FCF device 204 may form an Ethernet aggregated interface 604. Similarly, the grouping engine 405 provided by the FC switch 206 may group the internal ports of the Ethernet switch processor that are mapped to the FC PHYs that are provided by the converter 406 and coupled to the ports 410 a and 410 b that would otherwise make up FC trunk group between the FCF device 204 and the FC switch 206. As illustrated, the grouping of the internal ports of the Ethernet switch processor in the FC switch 206 may form an Ethernet aggregated interface 606.

In an example, the grouping engine 405 may group internal ports of the Ethernet switch processor in the FCF device 204 and the FC switch 206 according to an aggregation protocol such that the aggregated interface 606 may be a static link aggregation group (LAG). In various embodiments, the grouping engine 405 may group the internal ports to provide the Ethernet aggregated interfaces 604 and 606 according to an aggregation command that is provided by an administrator via, for example, a command line interface and that configures a Ethernet link aggregation table that includes an identifier assigned to the Ethernet aggregated interface 604 or 606, port identifiers of the internal ports of the Ethernet switch processor that are included in the Ethernet aggregated interface 604 or 606, and/or any other Ethernet aggregated interface information that would be apparent to one of skill in the art in possession of the present disclosure.

The method 500 may then proceed to block 504 where the FC PHYs that are provided by the converter and that are included in the Ethernet aggregated interface are configured with the same FC PHY configuration. In an embodiment of block 504, and with reference to the simulated FC trunking system 600 of FIG. 6, the grouping engine 405 of the FCF device 204 may configure the FC PHYs of the ports 412 a and 412 b, which are mapped to the internal ports of the Ethernet switch processor that are provided in the Ethernet aggregated interface 604, with the same FC PHY configurations. For example, the FC PHYs of the Ethernet aggregated interface 604 may be configured with the same vfabric configuration provided by a vfabric configuration file. In some examples, the vfabric configuration file may include an FCoE virtual local area network (VLAN) (FCoE VLAN) field, an FCoE MAC address prefix (FCoE FCMAP) field, and/or any other FC PHY configuration fields that would be apparent to one of skill in the art in possession of the present disclosure. Each of these FC PHY configuration fields provides a FC PHY configuration value (e.g., FCoE VLAN: “1001”, FCoE FCoE FCMAP: “0XEFC00”). In an embodiment, FC PHY configuration values for corresponding FC PHY configuration fields may be the same for each FC PHY of the Ethernet aggregated interface 604.

Similarly, the grouping engine 405 of the FC switch 206 may configure the FC PHYs of the ports 410 a and 410 b, which are mapped to the internal ports of the Ethernet switch processor that are provided in the Ethernet aggregated interface 606, with the same FC PHY configurations. For example, the FC PHYs of the Ethernet aggregated interface 606 may be configured with the same vfabric configuration provided by a vfabric configuration file. In some examples, the vfabric configuration file may include an FCoE VLAN field, an FCoE FCMAP field, and/or any other FC PHY configuration fields that would be apparent to one of skill in the art in possession of the present disclosure. Each of these FC PHY configuration fields provides a FC PHY configuration value (e.g., FCoE VLAN: “1001”, FCoE FCoE FCMAP: “0XEFC00”). In an embodiment, FC PHY configuration values for corresponding FC PHY configuration fields may be the same for each FC PHY of the Ethernet aggregated interface 606. In an embodiment, the FC PHY configurations of the FC PHYs of the Ethernet aggregated interface 606 may be the same as the FC PHY configurations of the FC PHYs of the Ethernet aggregated interface 604.

In various embodiments, upon successful fabric login between the FCF device 204 and the FC switch 206, buffer-to-buffer credits (BB_credits) may be programmed on all FC PHYs that are included on the aggregated interfaces 604 and/or 606. As would be understood by one of skill in the art in possession of the present disclosure, BB_credits are a flow-control mechanism that operates to ensure that FC interfaces do not drop frames, and are negotiated on a per-hop basis. In some embodiments, the BB_credits may only be used on FC PHYs, but not on virtual Fibre Channel interfaces.

The method 500 may proceed to block 506 where the Fibre Channel over Ethernet (FCoE) traffic that is provided by the Ethernet switch processor is load balanced between the first Ethernet link and the second Ethernet link. In an embodiment of block 506, and with reference to the simulated FC trunking system 600 in FIG. 6, egress FCoE traffic from the protocol processing engine 404 of the Ethernet switch processor may be load balanced by the grouping engine 405. The grouping engine 405 may include one or more load balancing algorithms that may be selected based on the role of the FC networking device 400. For example, an FCF device load balancing algorithm may be selected when the FC networking device 400 is the FCF device 204, and an FC switch load balancing algorithm may be selected when the FC networking device 400 is the FC switch 206. In a specific example, the FCF device load balancing algorithm may provide for the recognition of FCoE traffic at the Ethernet switch processor that is destined for a target communication system 208 a that is coupled to the FCF device 204 through the FC switch 206, and cause the Ethernet aggregated interface 604 to be utilized. Furthermore, the FCF device load balancing algorithm may provide for the load balancing or the hashing of egress FCoE traffic received over the Ethernet links 416 a and 416 b from the Ethernet switch processor based on a source identifier included in the FCoE traffic that identifies the source of the FCoE traffic. For example, if the server device 202 includes a plurality of servers that each have their own server identifier (e.g., a server MAC address), FCoE traffic that originates from a server in the server device 202 and that includes an odd numbered MAC address may be provided on the Ethernet link 416 a, while FCoE traffic that originates from a server with an even numbered MAC address may be provided on the Ethernet link 416 b. In another example, particular source identifiers may be assigned to specific Ethernet links (e.g., either of the links I in the Ethernet aggregated interface 606.) In other examples, the FCF load balancing algorithm may provide for the performance of exchange based hashing on the egress FCoE traffic. While specific FCF device load balancing algorithms have been described, one of skill in the art in possession of the present disclosure would recognize that other hashing/load balancing algorithms may be used without departing from the scope of the present disclosure.

In the simulated FC trunking system 600 illustrated in FIG. 6, the FCoE traffic that is provided on the Ethernet link 416 a may be converted to FC traffic by the FCoE-to-FC engine 408 b provided by the FC PHY included in the converter 408 that is coupled to the Ethernet link 416 a. The FC traffic may then be transmitted via the port 412 a that is mapped to the Ethernet link 416 a, and provided over the FC link 602 a. The FC switch 206 may receive the FC traffic on the port 410 a, and provide the FC traffic to the FC PHY of the converter 406 for the port 410 a. The FC-to-FCoE engine 406 a may convert the FC traffic to FCoE traffic, and provide the FCoE traffic to the protocol processing engine 404 of the FC switch 206 via the Ethernet link 414 a. The protocol processing engine 404 may then process the FCoE traffic and provided it to the converter 408 of the FC switch 206 (not illustrated in FIG. 6). The converter 408 of the FC switch 206 may then convert the FCoE traffic to FC traffic and provide it to the FC storage system 208.

Similarly, the FCoE traffic that is provided on the Ethernet link 416 b may be converted to FC traffic by the FCoE-to-FC engine 408 b provided by the FC PHY included in the converter 408 that is coupled to the Ethernet link 416 b. The FC traffic may then be transmitted via the port 412 b that is mapped to the Ethernet link 416 b, and provided over the FC link 602 b. The FC switch 206 may then receive the FC traffic on the port 410 b and provide the FC traffic to the FC PHY of the converter 406 for the port 410 b. The FC-to-FCoE engine 406 a may then convert the FC traffic to FCoE traffic, and provide the FCoE traffic to the protocol processing engine 404 of the FC switch 206 via the Ethernet link 414 b. The protocol processing engine 404 may then process the FCoE traffic, and provide the FCoE traffic to the converter 408 of the FC switch 206. The converter 408 of the FC switch 206 may then convert the FCoE traffic to FC traffic and provide it to the FC storage system 208.

In another example, when the FC networking device 400 is the FC switch 206, the FC switch load balancing algorithm may be selected. The FC switch load balancing algorithm may provide for the recognition of FCoE traffic at the Ethernet switch processor of the FC switch 206 that is destined for an initiator communication system 202 a that is coupled to the FC switch 206 through the FCF device 204, and thus the utilization of the Ethernet aggregated interface 606 of the FC switch 206. The FC switch load balancing algorithm may then provide for load balancing or hashing of egress FCoE traffic over the Ethernet links 414 a and 414 b from the Ethernet switch processor of the FC switch 206 based on a destination identifier included in the FCoE traffic that identifies the destination of the FCoE traffic. For example, if the server device 202 includes a plurality of servers that each have their own server identifier (e.g., a server MAC address), FCoE traffic destined to a server of the server device 202 with an odd numbered MAC address may be provided on the Ethernet link 414 a, while the FCoE traffic destined to a server with an even numbered MAC address may be provided on the Ethernet link 414 b. In another example, particular destination identifiers may be assigned to specific Ethernet links of the Ethernet aggregated interface 606. In other examples, the FC switch load balancing algorithm may provide for the performance of exchange based hashing on the egress FCoE traffic. While specific FC switch load balancing algorithms have been described, one of skill in the art in possession of the present disclosure will recognize that other hashing/load balancing algorithms may be used without departing from the scope of the present disclosure.

In the simulated FC trunking system 600 illustrated in FIG. 6, the FCoE traffic that is provided on the Ethernet link 414 a may be converted to FC traffic by the FCoE-to-FC engine 406 b provided by the FC PHY included in the converter 406 that is coupled to the Ethernet link 414 a of the FC switch 206. The FC traffic may then be transmitted via the port 410 a that is mapped to the Ethernet link 414 a, and provided over the FC link 602 a. The FCF device 204 may then receive the FC traffic on the port 412 a, and provide the FC traffic to the FC PHY of the converter 408 coupled to the port 412 a. The FC-to-FCoE engine 408 a may then convert the FC traffic to FCoE traffic, and provide the FCoE traffic to the protocol processing engine 404 of the FCF device 204 via the Ethernet link 416 a. The protocol processing engine 404 may then process the FCoE traffic, and provided it to the converter 406 of the FCF device 204 (not illustrated in FIG. 6). The converter 406 of the FCF device 204 may then convert the FCoE traffic to FC traffic, and provide it to the server device 202. However, in other embodiments, the protocol processing engine 404 may send the FCoE traffic directly to the server device 202 without converting the FCoE traffic to FC traffic.

Similarly, the FCoE traffic that is provided on the Ethernet link 414 b may be converted to FC traffic by the FCoE-to-FC engine 406 b provided by the FC PHY included in the converter 406 that is coupled to the Ethernet link 414 b. The FC traffic may then be transmitted via the port 410 b of the FC switch 206 that is mapped to the Ethernet link 414 b, and provided over the FC link 602 b. The FCF device 204 may then receive the FC traffic on the port 412 b, and provide the FC traffic to the FC PHY of the converter 408 coupled to the port 412 b. The FC-to-FCoE engine 408 a may then convert the FC traffic to FCoE traffic, and provide the FCoE traffic to the protocol processing engine 404 of the FCF device 204 via the Ethernet link 416 b. The protocol processing engine 404 may then process the FCoE traffic, and provide the FCoE to the converter 406 of the FCF device 204. The converter 406 of the FCF device 204 may then convert the FCoE traffic to FC traffic, and provide it to the FC storage system 208. However, in other embodiments, the protocol processing engine 404 may send the FCoE traffic directly to the server device 202 without converting the FCoE traffic to FC traffic.

As discussed above in conjunction with FIG. 6, the Ethernet links 416 a and 416 b are grouped together as the Ethernet aggregation interface 604, where the Ethernet aggregation interface 604 may be a static link aggregation group (LAG). As such, in the FCF device 204, the FC PHYs, which are provided by the converter 408 and mapped to the Ethernet links 416 a and 416 b, are programmed to have the same fibre-channel-forwarder media-access-control (FCF MAC) of the Ethernet aggregation interface. Also, for each Ethernet aggregation interface, the Ethernet switch processor (or equivalently Ethernet network processor NPU) included in the protocol processing engine 404 of the FCF device 204 generates only one fabric login (FLOGI) that is used to configure the simulated FC trunking system 600.

FIG. 7 is a flow chart illustrating an embodiment of a method 700 for processing a FLOGI on the simulated FC trunking system 600 of FIG. 6. The converter 408 in the FCF device 204 includes two Ethernet ports that are coupled to the Ethernet links 416 a and 416 b, respectively. Similarly, the converter 406 in the FC switch 206 includes two Ethernet ports that are coupled to the Ethernet links 414 a and 414 b, respectively. The method 700 begins at block 702, where all of the Ethernet ports, which are coupled to the trunk members 416 a and 416 b of the Ethernet aggregated interface 604 and located on the converter 408, are programmed with a FCF MAC of the Ethernet aggregated interface 604. At step 704, the Ethernet switch processor included in the protocol processing engine 404 of the FCF device 204 generates only one fabric login (FLOGI) for the Ethernet aggregated interface 604. Then, at block 706, the FLOGI is hashed over the trunk members 416 a and 416 b of the Ethernet aggregated interface 604 so that the FLOGI is sent to the FC switch 206 (more specifically to the Ethernet switch processor included in the protocol processing engine 404 of the FC switch 206) through one of the trunk members of the Ethernet aggregated interface 604.

At block 708, upon receiving the FLOGI, the Ethernet switch processor included in the protocol processing engine 404 of the FC switch 206 generates an acknowledgement signal, such as a FLOGI link service accept (LS_ACC), and hashes the FLOGI LS_ACC over the trunk members 414 a and 414 b of the Ethernet aggregated interface 606 so that the FLOGI LS_ACC is sent to the FCF device 204 through one of the trunk members of the Ethernet aggregated interface 606. At block 710, all of the FC ports (410 a and 410 b) on the FC switch 206, which are coupled to the FC links 602 a and 602 b and correspond to the trunk members 414 a and 414 b of the simulate FC trunk 606, are programmed with the buffer-to-buffer (BB) credit value included in the received FLOGI. At block 712, all of the FC ports (412 a and 412 b) on the FCF device 204, which correspond to the members of the Ethernet aggregated interface 604 and coupled to the FC links 602 a and 602 b, are programmed with the buffer-to-buffer (BB) credit value included in the FLOGI LS_ACC.

FIG. 8 is a schematic view illustrating an embodiment of a simulated FC trunking system 800. As shown in FIG. 8, the simulated FC trunking system 800 is similar to the system 600, with the difference that the FC trunking system 800 is configured to add/delete a trunk member to/from an Ethernet aggregation interface. More specifically, an Ethernet link 416 c is added as a new trunking member to the existing Ethernet aggregation interface 604 to thereby form a new Ethernet aggregation interface 804. Also, the added Ethernet link 416 c is coupled to the N_port 412 c that is coupled to the FC link 602 c. Similarly, the Ethernet aggregation interface 806 in the FC switch 206 includes a new trunk member 414 c, which is an Ethernet link between the converter 406 and protocol processing engine 404. Also, the added Ethernet link 414 c is coupled to the FC port 410 c that is coupled to the FC link 602 c. For the purpose of illustration, only one trunk member is added to the existing trunk group 604 (and 606). However, it should be apparent to those of ordinary skill in the art that other suitable number of trunk members can be added to the existing trunk group.

It is noted that the operations and functions of the components of the simulated FC trunking system 800 is similar to their counterpart of the simulated FC trunking system 600. One of the differences between the two systems 600 and 800 is that the system 800 balances the FC traffic load using the three Ethernet links 416 a, 416 b, and 416 c while the system 600 balances the FC traffic load using the two Ethernet links 416 a and 416 b.

FIG. 9 is a flow chart illustrating an embodiment of a method 900 for adding a trunk member to a simulated FC trunking system. The method 900 begins at block 902. At block 902, a new trunk member is added to the Ethernet aggregation interface. By way of example, the Ethernet link 416 c (and 414 c) is added as a new trunk member to the Ethernet aggregation interface 604 (and 606) in FIG. 6, causing the Ethernet aggregation interface 804 (and 806) to include three trunk members. At block 904, the FC PHY converter 408 (and 406) provides a FC PHY to the added trunk member 416 c (and 414 c). At block 906, the FC PHY of the added trunk member 416 c (and 414 c) is programmed with the BB credit value that is already programmed in the FC PHYs of existing trunk members 416 a and 416 b (and 414 a and 414 b). At block 908, the FC PHY converter 408 (and 406) programs the FC PHY of added trunk member with the FCF MAC of the Ethernet aggregated interface 804 (and 604), where the existing trunk members 416 a and 416 b (and 414 a and 414 b) have been already programmed with the FCF MAC of the Ethernet aggregated interface 604 (and 606).

In embodiments, a trunk member may be deleted from a trunk group. For instance, the Ethernet link 416 c may be deleted from the Ethernet aggregation interface 804 in FIG. 8, causing the simulated FC trunking system 800 to have the same configuration as the simulated FC trunking system 600 in FIG. 6. In some cases, the Ethernet aggregation group may include only one trunk member. In such a case, the FCF device 204 sends a status notice, such as logout/clear-virtual-link (LOGO/CVL), to an end device, such as server device 202, so that the end device is informed of the trunk status and stops sending FC traffic to the FCF device 204.

FIG. 10 is a flow chart illustrating an embodiment of a method 1000 for deleting a trunk member from a simulated FC trunking system. The method 1000 beings at block 1002. At block 1002, a trunk member, such as 416 c, is deleted from the trunk group, such as Ethernet aggregation interface 804. Then, the simulated FC trunking system 800 is configured to have the same configuration as the simulated FC trunking system 600. At block 1004, it is determined whether there is any remaining trunk member in the trunk group. If the answer to block 1004 is negative, the method 1000 proceeds to block 1008 so that the simulated FC trunking system 600 resumes the network functions. Otherwise, the FCF device 204 sends LOGO/CVL to an end device, such as the server device 202, so that the end device is informed of the trunk status and stops sending FC traffic to the FCF device 204.

In embodiments, systems and methods have been described that provide for simulated FC trunking in FC networking devices that include an Ethernet switch processor by grouping internal Ethernet ports of the Ethernet switch processor that provide Ethernet links between the Ethernet switch processor and the FC PHYs that convert FCoE traffic to FC traffic before being provided over a FC link to another FC networking device. After aggregating the Ethernet links to form an Ethernet aggregated interface, FCoE traffic may be load balanced on the Ethernet links of the Ethernet aggregated interface, and provided as FC traffic over FC links (which would otherwise be grouped in conventional FC trunking systems) to other FC networking devices. The grouped Ethernet links simulate the FC trunking without the FC level handshaking operations required in conventional FC trunking systems, which eliminates the need for expensive, proprietary FC switch chips that are complex and inefficient.

Although illustrative embodiments have been shown and described, a wide range of modification, change and substitution is contemplated in the foregoing disclosure and in some instances, some features of the embodiments may be employed without a corresponding use of other features. Accordingly, it is appropriate that the appended claims be construed broadly and in a manner consistent with the scope of the embodiments disclosed herein. 

What is claimed is:
 1. An information handling system for managing a communication trunk in a fibre channel (FC) networking system, comprising: a first networking device including a first switch processor and a first converter that is communicatively coupled to the first switch processor via a first plurality of Ethernet links, the first plurality of Ethernet links being grouped as a first Ethernet aggregation, the first networking device being configured to load balance data traffic across the first plurality of Ethernet links; and each Ethernet link of the first plurality of Ethernet links being mapped to a corresponding FC link of a plurality of FC links of the first networking device, wherein the first networking device is configured to: apply an FC configuration on each FC interface of the plurality of FC links; for establishing an FC trunk comprising the plurality of FC links associated with the first Ethernet aggregation, generate only one fiber login (FLOGI) for the FC trunk associated with the first Ethernet aggregation; and generate, using the first switch processor, and send the FLOGI to a second networking device via the first Ethernet aggregation, the second networking device being communicatively coupled to the first networking device via the plurality of FC links.
 2. The information handling system of claim 1, wherein the first networking device is configured to send the FLOGI by hashing the FLOGI among the first plurality of Ethernet links.
 3. The information handling system of claim 1, wherein the second networking device comprises: a second switch processor; and a second converter that is communicatively coupled to the second switch processor via a second plurality of Ethernet links, the second plurality of Ethernet links being grouped as a second Ethernet aggregation corresponding to the first Ethernet aggregation, each Ethernet link of the second plurality of second Ethernet links being mapped to a corresponding FC link of the plurality of FC links of the second networking device; wherein the second networking device is configured to: load balance data traffic for the first networking device across the second plurality of Ethernet links of the second Ethernet aggregation.
 4. The information handling system of claim 3, wherein the second networking device is further configured to: responsive to receiving the FLOGI, generate an acknowledgement signal; and send the acknowledgement signal to the first networking device via the second Ethernet aggregation.
 5. The information handling system of claim 4, wherein the second networking device sends the acknowledgement signal by hashing the acknowledgement signal among the second plurality of Ethernet links.
 6. The information handling system of claim 5, wherein the first networking device includes a plurality of FC ports that are communicatively coupled to the plurality of FC links, respectively, and wherein the first converter is configured to program all of the plurality of FC ports with a buffer-to-buffer (BB) credit value included in the acknowledgement signal.
 7. The information handling system of claim 3, wherein each of the first plurality of Ethernet links is mapped to a corresponding one of the second plurality of Ethernet links.
 8. The information handling system of claim 1, wherein the second networking device includes a plurality of FC ports that are communicatively coupled to the plurality of FC links, respectively, and wherein the second converter is configured to program all of the plurality of FC ports with a buffer-to-buffer (BB) credit value included in the FLOGI.
 9. The information handling system of claim 1, wherein the first converter is further configured to: responsive to adding an Ethernet link to the first Ethernet aggregation interface, provide a FC PHY to the added Ethernet link, program the FC PHY with a buffer-to-buffer (BB) credit value of other Ethernet links in the first Ethernet aggregation, and program the FC PHY with a fibre-channel-forwarder media-access-control (FCF MAC) of a FC trunk associated with the first Ethernet aggregation.
 10. The information handling system of claim 1, wherein the first converter is further configured to: responsive to deleting an Ethernet link from the first Ethernet aggregation, sends a status notice to an end device that is communicatively coupled to the first networking device if there is no remaining Ethernet link in the first Ethernet aggregation.
 11. A computer-implemented method for managing a communication trunk in a networking device, comprising: grouping the plurality of Ethernet links that provide communication links between a network processing unit and a converter as an Ethernet link aggregation group (LAG), wherein a data traffic to be sent to another networking device is load balanced across the plurality of Ethernet links of the LAG; mapping Ethernet links of a plurality of Ethernet links to a plurality of fibre channel (FC) interfaces; mapping the LAG to a logical FC trunk, in which a configuration is applied on all FC interfaces that are part of the logical FC trunk; for configuring an FC trunk, generating only one fiber login (FLOGI) for the FC trunk comprising the plurality of FC interfaces, which corresponds to the Ethernet link aggregated group; and sending the FLOGI to another networking device via at least one of the plurality of FC interfaces.
 12. The computer-implemented method of claim 11, wherein the step of sending the FLOGI includes hashing the FLOGI among the plurality of Ethernet links.
 13. The computer-implemented method of claim 11, wherein the method further comprises: receiving an acknowledgement signal that indicates an acceptance of the FLOGI and includes a buffer-to-buffer (BB) credit value; and programming all of the plurality of FC interfaces with a buffer-to-buffer (BB) credit value.
 14. The computer-implemented method of claim 11, further comprising: responsive to adding an Ethernet link to the Ethernet link aggregation group, mapping an FC interface to the added Ethernet link; programming the FC interface with a buffer-to-buffer (BB) credit value of the plurality of Ethernet links; and programming the FC interface with a fibre-channel-forwarder media-access-control (FCF MAC) of a communication trunk associated with the Ethernet link aggregation group.
 15. The computer-implemented method of claim 11, further comprising: responsive to deleting an Ethernet link from the Ethernet link aggregation group, determining whether there is any remaining Ethernet links in the Ethernet link aggregation group; and responsive to a negative answer to the determination, sending a status notice to an end device.
 16. A non-transitory computer-readable medium or media comprising one or more sequences of instructions which, when executed by one or more processors of a networking device, causes steps to be performed comprising: grouping the plurality of Ethernet links that provide communication links between a network processing unit and a converter as an Ethernet link aggregation group (LAG), wherein a data traffic to be sent to another networking device is load balanced across the plurality of Ethernet links of the LAG; mapping Ethernet links of a plurality of Ethernet links to a plurality of fibre channel (FC) interfaces; mapping the LAG to a logical FC trunk, in which a configuration is applied on all FC interfaces that are part of the logical FC trunk; for configuring an FC trunk, generating only one fiber login (FLOGI) for the FC trunk comprising the plurality of FC interfaces, which corresponds to the Ethernet link aggregated group; and sending the FLOGI to another networking device via at least one of the plurality of FC interfaces.
 17. The non-transitory computer-readable medium or media of claim 16, wherein the step of sending the FLOGI includes hashing the FLOGI among the plurality of Ethernet links.
 18. The non-transitory computer-readable medium or media of claim 16 further comprising one or more sequences of instructions which, when executed by the one or more processors, causes steps to be performed comprising: receiving an acknowledgement signal that indicates an acceptance of the FLOGI and includes a buffer-to-buffer (BB) credit value; and programming all of the plurality of FC interfaces with a buffer-to-buffer (BB) credit value.
 19. The non-transitory computer-readable medium or media of claim 16, further comprising one or more sequences of instructions which, when executed by the one or more processors, causes steps to be performed comprising: responsive to adding an Ethernet link to the Ethernet link aggregation group, mapping an FC interface to the added Ethernet link; programming the FC interface with a buffer-to-buffer (BB) credit value of the plurality of Ethernet links; and programming the FC interface with a fibre-channel-forwarder media-access-control (FCF MAC) of a communication trunk associated with the Ethernet link aggregation group.
 20. The non-transitory computer-readable medium or media of claim 16, further comprising one or more sequences of instructions which, when executed by the one or more processors, causes steps to be performed comprising: responsive to deleting an Ethernet link from the Ethernet link aggregation group, determining whether there is any remaining Ethernet links in the Ethernet link aggregation group; and responsive to a negative answer to the determination, sending a status notice to an end device. 